Access to mobile location related information

ABSTRACT

Access to location information related to mobile devices is disclosed. A component can receive a subscription request related to returning location related data associated with a set of network event locating system (NELOS) information. NELOS information can be received from a NELOS component and can be derived from timed fingerprint location (TFL) information associated with a user equipment (UE). TFL information and NELOS information can be distinct from location information determined from conventional techniques which can provide for additional benefit. The subscription request can indicate continuing access to location information without subsequent requests. Moreover, access can be via a push of information to a subscribing device.

TECHNICAL FIELD

The disclosed subject matter relates to facilitating access to locationinformation related to mobile devices, including sourcing locationinformation related to mobile devices to a third party device inresponse to an agreement made between a provider device and a subscriberdevice.

BACKGROUND

By way of brief background, mobile location information can be a highlyvalued data component for a multitude of applications. Mobile locationinformation can be leveraged to facilitate delivery of real-timeadvertising, notifications, to establish behavior patterns ofindividuals, aggregated into anonymized data sets for optimal placementof infrastructure and/or services, for law enforcement purposes, etc.Conventional network location technologies can generally be associatedwith limitations, such as being limited to a particular carrier,particular device type, or require rollout of additional infrastructure,etc., that can, for example, limit success rates to anywhere betweenabout 15% to 80%. This broad range of possible failures, e.g., an about20% to 85% failure rate based on the about 15-80% success rate, forcapturing relevant location data can be a significant cause ofuncertainty among consumers of such location information, e.g., thesignificant uncertainty can impact pricing, confidence, or reliance onconventionally ascertained location information. As an example, wherelocation data for a region is requested from a carrier, the successfulreturn of location data for all mobile devices in that region can belimited by the percentage of customers using the carrier as opposed toother carriers. The successful return of location data can further belimited in the example for devices also needing to be enabled for thelocation technology being employed, as opposed to older devices that maynot have said location technology. Moreover, the successful return oflocation data can also be further limited by the scope of infrastructurethe example carrier has rolled out to actually capture potentiallocation information. Other deficiencies of conventional locationinformation technologies may become apparent from the description of thevarious embodiments of the subject application below.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of an example system that facilitates accessto mobile device location information in accordance with aspects of thesubject disclosure.

FIG. 2 is a depiction of an example system that facilitates access tomobile device location information by a third party in response to asubscription request in accordance with aspects of the subjectdisclosure.

FIG. 3 illustrates an example system that facilitates access to mobiledevice location information and analysis in accordance with aspects ofthe subject disclosure.

FIG. 4 illustrates an example system that facilitates access to mobiledevice location information subject to subscription rules in accordancewith aspects of the subject disclosure.

FIG. 5 illustrates an example system that facilitates access to mobiledevice location information via a cloud-based deployment in accordancewith aspects of the subject disclosure.

FIG. 6 illustrates an example method facilitating access to mobiledevice location information in accordance with aspects of the subjectdisclosure.

FIG. 7 depicts an example method facilitating a push of mobile devicelocation information and employing control information in accordancewith aspects of the subject disclosure.

FIG. 8 illustrates an example method facilitating access to mobiledevice location information and analysis in accordance with aspects ofthe subject disclosure.

FIG. 9 depicts an example schematic block diagram of a computingenvironment with which the disclosed subject matter can interact, or inwhich aspects can be implemented.

FIG. 10 illustrates an example block diagram of a computing systemoperable to execute the disclosed systems and methods in accordance withan embodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

Conventional network location technologies can be associated withnotable limitations, e.g., particular carrier, particular device type,supporting infrastructure, etc. A lack of third party consumerconfidence in the reliability of mobile location information can affectthe consumption of such information by a third party consumer.Improvements in the mobile location information technology can greatlyimprove on conventional technologies.

In contrast to conventional network location technologies, the instantdisclosure can provide for near real time access to location recordsthat can be device/carrier agnostic. Additionally, in some embodiments,location related information can be pushed out to a third party as theinformation becomes available, thereby reducing the need for the thirdparty to make multiple requests for location related data.

Some embodiments can incorporate rules that facilitate access tolocation information of mobile devices in an idle state, which canprovide rich context with regard to the location of a mobile devicewithout significantly taxing the resources of the mobile device as mightbe expected in conventional technologies.

Additional embodiments can apply rules to enable control of datacapture, data analysis, and subscription management, for indicatedmobile device identities. As an example, where a third party subscriberidentifies a plurality of mobile devices for which location relatedinformation is desired, rules can be applied that can apply to all,some, one, or none of the plurality of mobile devices, e.g., a firstrule can request that location information for all devices be providedat least hourly, a second rule can request that location informationwithin a determined distance of a locus be provided as soon as possible,and a third rule can request that mobile device identities associatedwith a user age value of less than 18 years be withheld, etc. Dependingon how the first, second, third rule, etc., are organized, these rulescan result in access to different data packages for the third partysubscriber according to the goals of the third party subscriber.

In some embodiments, location data subscription components can beintegrated into carrier-side equipment or devices. In other embodiments,location data subscription components can be operated on non-carriercontrolled equipment or devices. As an example, a location datasubscription components can be part of a carrier gateway device, acarrier server, a carrier NodeB, etc. As another example, a locationdata subscription components operated in a virtual machine in a cloudenvironment, operate on a non-carrier corporate server, on an mobilevirtual network operator (MVNO) gateway, etc.

Certain embodiments of the disclosed subject matter can provide forinteraction with a UE location data source to provide for some aspectsof the instant disclosure. As an example, a UE can receive instructionsor a rule directing that the UE cache idle-state timing information suchthat this idle-state information can be communicated when the UE is in afuture active-state. As another example, loci can be provided to the UEalong with a rule indicating that the UE should enter an active-statewhen the UE position satisfies a rule related to a locus of the loci. Asa further example, a UE can receive a rule requesting that locationinformation be provided in conjunction with an event, date, time,location, state transition, device parameter such as battery level,processor usage, available memory, etc., weather condition, use of anapplication on the UE, schedule, etc.

It will be noted that the use of the terms “location”, “location data”,or other similar terms, can expressly include information identifying alocation, region, area, etc., timing information related to determininga location, additional information in addition to a location or timinginformation, such as a time stamp, accuracy indicator, identifier(s),longitude/latitude/altitude, distance, proximity, beacon identities,images, sounds, motion, device parameters, etc., or derivatives oflocation or timing information such as direction of travel, speed,altitude, proximity, distance, mode or travel, moving or stopped time,etc., and, as such, should be generally treated broadly unless they areexplicitly or inherently used in narrow manner. Moreover, it will befurther noted that the terms “location”, “location data”, or othersimilar terms, as used herein, can expressly include timed fingerprintlocation (TFL) information, network event locating system (NELOS)information, and other similar types of information. Similarly, theterms “TFL”, “TFL information”, “NELOS”, “NELOS information”, or similarterms as used herein can expressly include location, location data, orthe like.

TFL information can include location information or timing informationrelated to determining a location. As such, a TFL component or NELOScomponent can facilitate access to location information for a UE, andTFL information can be information from systems in, or associated with,a timed fingerprint location wireless environment, such as a TFLcomponent of a wireless telecommunications carrier, a NELOS component,etc. As a non-limiting example, a mobile device, including mobiledevices not equipped with a GPS-type system, can be located by lookingup timing information associated with the mobile device from a TFLinformation component or NELOS component.

In an aspect, TFL information can include information related todetermining a differential value for a NodeB site pair and a bin gridframe of a bin grid frame array. A centroid region, e.g., possiblelocations between a NodeB site pair, for an observed time valueassociated with the NodeB site pair (NBSP) can be calculated and isrelated to a determined value, e.g., in units of chip, from the pair ofNodeBs. When UE time data is accessed, a value look-up can be initiated,e.g., a lookup for “DV(?,X)”. Relevant NBSPs can be prioritized as partof the look-up event. Further, the relevant NBSPs can be employed as anindex to lookup a first primary set. As an example, time data for a UEcan be accessed in relation to a locating event in a TFL wirelesscarrier environment. In this example, it can be determined that a NBSP,with a first reference frame, be used for primary set lookup with thecomputed DV(?,X) value as the index. This can, for example, return a setof bin grid frame locations forming a hyperbola between the NodeBs ofthe NBSP. A second lookup can then be performed for an additionalrelevant NBSP, with a second reference frame, using the same valueDV(?,X), as an index into the data set. Continuing the example, thereturned set for the look up with second NBSP can return a second set ofbin grid frames. Thus, the UE is likely located in both sets of bin gridframes. Therefore, where the UE is likely in both sets, it is probablethat the location for the UE is at an intersection of the two sets.Additional NBSPs can be included to narrow the possible locations of theUE further by providing additional intersections among relevant bin gridsets. As such, employing TFL information for location determination isdemonstrably different from conventional location determinationtechniques or systems such as GPS, eGPS, triangulation ormultilateration in wireless carrier environments, near field techniques,or proximity sensors. TFL information can be employed for mobile devicesin active states, and in some embodiments, can also be employed formobile device in idle states.

In an aspect, TFL information can be particularly well suited tolocation analytic technologies in that TFL information lookup generallyrequires less computation that other location technologies. For example,in conventional multilateration systems, complex math is typicallyemployed to convert a plurality of measured signals into a location. Incontrast, TFL information is generally pre-computed and could employsimple lookup techniques to garner probable locations of a UE based onoverlapping bin grid locations for a plurality of NodeB Site Pairs(NBSPs). Moreover, timing signals can be captured by a UE between activeconnections to a carrier to allow location histories, e.g., viahistorical TFL information on the UE, of devices with less consumptionof network resources, battery power, etc.

In a further aspect, TFL information can be acquired based on timingsignals already being received by a typical UE and, as such, additionalpower need not typically be expended, for example, on an additionalradio receiver as would be common in more conventional locationtechnologies such as GPS, in going active for conventional technologiessuch as trilateration/triangulation, etc. As an example, in contrast toa GPS system having a GPS receiver to receive GPS signals, a TFL enabledsmartphone can employ wireless radio timing signals already associatedwith the wireless cellular service of the smartphone to determinelocation such that both location information and cellular service areaccommodated on the same radio and additional energy for a second radioneed not be expended. As such, TFL information can be well suited toportable user equipment that typically is both highly power consciousand relatively processor limited as compared to their non-mobilecounterparts. It is to be appreciated that where the location of amobile device can be achieved with TFL information without bogging downa processor or further increasing battery depletion in the mobiledevice, the use of TFL information is well suited for location analyticsrelated to a mobile device.

In an embodiment, a system can comprise a processor and memory tofacilitate performance of operations comprising receiving a request formobile device location information from a subscribing device associatedwith a subscriber entity. In response to receiving NELOS informationrelated to a location of a mobile device, access to the location datacan be facilitated. This can be based on a parameter of the requestsatisfying a rule related to permission to access the location data.

In another embodiment, a method can comprise receiving a subscriptionrequest from a subscribing device. NELOS information related to alocation of a US can also be received. The subscribing device can accessa data deliverable comprising information related to the NELOSinformation based on the subscription request.

In a further embodiment, a computer readable storage device can compriseinstructions for receiving a request for mobile device locationinformation from a subscribing device associated with a subscriberidentity. Further, NELOS information related to a location of a mobiledevice can also be received. Location data can be generated in responseto an analysis of the NELOS information based on the request. Thelocation data can be shared with the subscribing device.

In an aspect, while terms like “user equipment (UE),” “mobile station,”“mobile,” subscriber station,” “subscriber equipment,” “accessterminal,” “terminal,” “handset,” and similar terminology, canconventionally refer to a wireless device utilized by a wirelessservices subscriber or user of a wireless communication service toreceive or convey data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream, in instances wherethere are multiple types of subscriptions, the terms can also refer toaspects of each subscription service. As an example, where a UE accessesa wireless cellular service according to a subscription with a wirelesscellular carrier, this can be accomplished via a femtocell that harvestsmetadata for a remotely located device according to a subscription withthe manufacturer of the femtocell. In this example, there is a UE thatis a subscriber device of the wireless cellular service and anothersubscriber device, i.e., the remote device, subscribing to a service ofthe femtocell manufacturer. As such, it will be noted, that the termsubscribing device, as used herein, can generally refer to a mobiledevice or UE, e.g., UE 250, 350, 450, etc., subscribing to a mobilecarrier service and/or, as dictated by context, can refer to otherdevices that subscribe to location services as provided in the contextof the currently disclosed subject matter, e.g., devices, such as 3^(rd)party component 220, etc., accessing SDD 142, 242, etc. as disclosed inmore detail herein below.

To the accomplishment of the foregoing and related ends, the disclosedsubject matter, then, comprises one or more of the features hereinaftermore fully described. The following description and the annexed drawingsset forth in detail certain illustrative aspects of the subject matter.However, these aspects are indicative of but a few of the various waysin which the principles of the subject matter can be employed. Otheraspects, advantages and novel features of the disclosed subject matterwill become apparent from the following detailed description whenconsidered in conjunction with the provided drawings.

FIG. 1 is an illustration of a system 100, which facilitates access tomobile device location information in accordance with aspects of thesubject disclosure. System 100 can comprise location data subscriptioncomponent (LDSC) 110. LDSC 110 can receive subscription request 122.Subscription request 122 can comprise a parameter related to subscriberdata deliverable (SDD) 142, such as frequency of reporting, a reportingtrigger such as an event, proximity, time, identifier(s), etc., a typeof returned data such as location, timing information, derivatives oflocation or timing information, etc., price, device, age, etc. LDSC 110can further receive NELOS data 132 which can comprise location datarelated to a mobile device or other UE. LDSC 110 can facilitate accessto SDD 142 based on NELOS data 132 and subscription request 122. SDD 142can comprise a location, location data, TFL information, NELOSinformation, derivatives thereof, or other related information.

In an embodiment, LDSC 110 can receive a location or location data,e.g., via NELOS data 132, from a UE. NELOS data 132 can be received froma NELOS component, e.g., NELOS component 230 in FIG. 2, etc., from a UEdirectly, or via another component such as a data store, cloudenvironment device, etc. NELOS data 132 can comprise TFL or TFLinformation. As such, NELOS data 132 can comprise near real timelocation or location data, historical location or location data, cachedlocation or location data, etc. The particulars of capturing,determining, or generating TFL, TFL information, or NELOS information isoutside of the scope of the instant disclosure except where moreparticularly pointed out herein and to note that these types of locationrelated information, e.g., TFL information, etc., are distinct from moreconventional types of location related information, such as that fromGPS, triangulation, trilateration, beacon ranging, etc. As such, the useof TFL, TFL information, NELOS information, NELOS technology, etc., incombination with the instant disclosure provides advantages overconventional technologies, such as, being device/provider independent,information sourcing that can consume less power and/or can consumefewer network resources, etc.

In an aspect, NELOS data 132 can be processed at LDSC 110 to generateSDD 142 that can then be made accessible to other components or devices.In an embodiment, NELOS data 132 can be passed as SDD 142 without changewhere no change is indicated in the analysis of NELOS data 132 in viewof subscription request 122, e.g., where subscription request 122indicates that SDD 142 should comprise all NELOS data 132, then SDD 142can be the same as NELOS data 132. In other embodiments, NELOS data 132can be processed, analyzed, etc., such that SDD 142 comprisesinformation derived from NELOS data 132, e.g., SDD 142 is not the sameas NELOS data 132. As an example, where LDSC 110 analyzes NELOS data 132and determines that it comprises private information, this privateinformation can be stripped out and the balance of the information canbe made available as SDD 142. As another example, LDSC 110 can receiveNELOS data 132 comprising timing information and can convert the timinginformation to location information such that SDD 142 comprises locationinformation rather than timing information. In a further example, LDSC110 can receive NELOS data 132 comprising information from a pluralityof UEs and an aggregate elements of this information to include in SDD142, such as where such aggregating is indicated in subscription request122. Numerous other examples are readily appreciated, and although notrecited herein for the sake of brevity, such examples are to beconsidered within the scope of the instant disclosure.

In an embodiment, LDSC 110 can make control information, rules, etc.,available to a NELOS component, such as NELOS component 230 in FIG. 2,etc., or to a UE, such as UE 250 of FIG. 2, etc. As an example, a rulecan be communicated to a UE via LDSC 110 that can allow the UE toselectively store location information, TFL information, etc., andreturn the stored information to LDSC 110 in accord with the rule. Thisaspect can enable a variety of component configurations comprising, forexample, UEs sourcing location information or timing information, NELOScomponents determining TFL information, LDSC 110 receiving NELOS data132, and making SDD 142 available to other components or devices notillustrated in system 100. Some of these component configurations areillustrated in subsequent figures, though not all configurations areillustrated for clarity and brevity, although all such configurationsare considered within the scope of the instant disclosure.

FIG. 2 is a depiction of a system 200 that can facilitate access tomobile device location information by a third party in response to asubscription request in accordance with aspects of the subjectdisclosure. System 200 can comprise LDSC 210. LDSC 210 can receivesubscription request 222 from third party component 230. Third partycomponent 230 can be a component or device associated with a thirdparty, e.g., other than the carrier identity and a user identityassociated with UE 250. As an example, third party component can be anemergency services or police component, an advertiser's server, amapping service's device, etc. Subscription request 222 can comprise aparameter related to SDD 242. LDSC 210 can further receive NELOS data232, from NELOS component 230, which can comprise location data relatedto UE 250. LDSC 210 can facilitate access to SDD 242 based on NELOS data232 and subscription request 222. SDD 242 can comprise a location,location data, TFL information, NELOS information, derivatives thereof,or other related information.

NELOS component 230 can receive TFL information 252 from UE 250. Assuch, NELOS component 230 can generate NELOS data 232 based on TFLinformation 252. In an embodiment NELOS data 232 can be the same as TFLinformation 252, e.g., NELOS component 230 can pass TFL information 252through as NELOS data 232. In other embodiments, NELOS data 232 can bedifferent from TFL information 252, such as where TFL information 252can comprise timing information that can be converted to locationinformation by NELOS component 230 such that NELOS data 232 can compriselocation information in place of, or in addition to, the timinginformation of TFL information 252.

In an aspect, UE 250 can be logically considered as located on auser-side of a communication link. As an example, UE 250 can beconsidered to be on the user-side of a radio link with a NodeB thatitself can be considered to be on a carrier-side of the radio link. In afurther similar aspect, NELOS component 230 and/or LDSC component 210can be logically considered as located on a carrier-side of acommunication link. As an example, NELOS component 230 and/or LDSCcomponent 210 can be located at a carrier core network component. Inanother similar aspect, third party component 220 can be logicallyconsidered to be located on a third party-side of a communication link.As an example, where LDSC 210 is located in a carrier core component, itcan be communicatively linked to third party component 220 via aninternet connection wherein third party component 220 is located otherthan on the carrier-side of the internet link(s). In an aspect, system200 can illustrate a possible end to end configuration highlightingsourcing of data from the user-side, processing of data at thecarrier-side, and delivery of data in response to a request from thethird party-side. System 200 is not intended to be limit the disclosurewhereas numerous other configurations are readily appreciated and wouldbe considered within the scope of the instant disclosure.

In an embodiment, LDSC 210 can receive a location or location data,e.g., TFL information 252, etc., via NELOS component 230, e.g., NELOSdata 232, from UE 250. NELOS data 232 can comprise TFL or TFLinformation 252. As such, NELOS data 232 can comprise near real timelocation or location data, historical location or location data, cachedlocation or location data, etc. These types of location relatedinformation, e.g., TFL information 252, etc., are distinct from moreconventional types of location related information, such as that fromGPS, triangulation, trilateration, beacon ranging, etc. As such, the useof TFL information 252, NELOS information 232, etc., in combination withthe instant disclosure can provide, as disclosed herein, advantages overconventional technologies.

In an aspect, NELOS data 232 can be processed at LDSC 210 to generateSDD 242. SDD 242 can be received by third party component 250. SDD 242can be responsive to parameters of subscription request 222. In anembodiment, subscription request 222 can represent a single SDD 242request, e.g., one-time access to SDD 242. In other embodiments,subscription request 222 can represent a plural SDD 242 request, e.g.,multiple access to updated SDD 242. In some embodiments, subscriptionrequest 222 can represent an ongoing SDD 242 request, e.g., ongoingaccess to updated SDD 242 within the scope of a subscription model. Inan embodiment, SDD 242 can be ‘pushed’ to third party component 220 inan automated manner. This push-model can reduce multiple requests foraccess to SDD 242 from third party component 220. In another embodiment,third party component 220 can ‘pull’ SDD 242 from LDSC 210, e.g.,requesting access to SDD 242, etc. In a further embodiment, LDSC 210 canpublish SDD 242 and third party component 220 can access the publishedSDD 242. Other techniques facilitating access to SDD 242 are also to beconsidered within the scope of the present disclosure even where notrecited for the sake of brevity.

FIG. 3 illustrates a system 300 that facilitates access to mobile devicelocation information and analysis in accordance with aspects of thesubject disclosure. System 300 can comprise LDSC 310. LDSC 310 canreceive subscription request 322. Subscription request 322 can comprisea parameter related to SDD 342. LDSC 310 can further receive NELOS data332, from NELOS component 330, which can comprise location data relatedto UE 350. LDSC 310 can facilitate access to SDD 342 based on NELOS data332 and subscription request 322. SDD 342 can comprise a location,location data, TFL information, NELOS information, derivatives thereof,or other related information.

NELOS component 330 can receive TFL information 352 from UE 350. Assuch, NELOS component 330 can generate NELOS data 332 based on TFLinformation 352. In an embodiment NELOS data 332 can be the same as TFLinformation 352, e.g., NELOS component 330 can pass TFL information 352through as NELOS data 332. In other embodiments, NELOS data 332 can bedifferent from TFL information 352, such as where TFL information 352can comprise timing information that can be converted to locationinformation by NELOS component 330 such that NELOS data 332 can compriselocation information in place of, or in addition to, the timinginformation of TFL information 352. As such, NELOS data 332 can comprisenear real time location or location data, historical location orlocation data, cached location or location data, etc. These types oflocation related information, e.g., TFL information 352, etc., aredistinct from more conventional types of location related information,such as that from GPS, triangulation, trilateration, beacon ranging,etc. As such, the use of TFL information 352, NELOS information 332,etc., in combination with the instant disclosure can provide, asdisclosed herein, advantages over conventional technologies.

In an aspect, NELOS data 332, once received by LDSC 310, can be storedat NELOS data store 314. NELOS data store 314 can further be employed tostore and update SDD 342, such as storing and updating SDD 342 betweenaccessed from a third party component, e.g., 220, etc. In an embodiment,LDSC 310 can receive more NELOS data 332 than can be associated withsubscription request 322, whereby LDSC 310 can store the pertinentportion of NELOS data 332 at NELOS data store 314. In anotherembodiment, NELOS data store 314 can retain excess NELOS data 332 toallow for potential updates to subscription request 322. As an example,where other subscription requests indicate a trend to include proximityto a sporting event for a particular geographic region, LDSC 310 canbegin storing proximity information at NELOS data store 314 for othersubscribers even though they may not yet have requested thatinformation. This can allow LDSC 310 to be more responsive in providingproximity information where the subscriptions are updated to requestthis additional information. LDSC 310 can analyze NELOS data 332 and/ordata stored on NELOS data store 314 via NELOS data analysis component316 to facilitate determining SDD 342. Nearly any analysis can beperformed at NELOS data analysis component 316. As an example, data canbe aggregated, personally identifying information can be removed,average values can be generated, trends can be determined, locations,modes of travel, etc.

In some embodiments, UE 350 can further comprise TFL information store354. TFL information store 354 can store TFL information related to UE350. In an aspect, this can be related to determining TFL information352. Further, TFL information store 354 can store TFL information basedon received TFL information retention rule 312. TFL informationretention rule 312 can be related to types of information to be retainedat TFL information store 354, amounts of information to be retained atTFL information store 354, filtering of information retained at TFLinformation store 354, etc. In an embodiment, TFL information 352 cancomprise information from TFL information store 354.

FIG. 4 illustrates a system 400 that facilitates access to mobile devicelocation information subject to subscription rules in accordance withaspects of the subject disclosure. System 400 can comprise LDSC 410.LDSC 410 can receive subscription request 422. Subscription request 422can comprise a parameter related to SDD 442. LDSC 410 can furtherreceive NELOS data 432, from NELOS component 430, which can compriselocation data related to UE 450. LDSC 410 can facilitate access to SDD442 based on NELOS data 432 and subscription request 422. SDD 442 cancomprise a location, location data, TFL information, NELOS information,derivatives thereof, or other related information.

NELOS component 430 can receive TFL information 452 from UE 450. Assuch, NELOS component 430 can generate NELOS data 432 based on TFLinformation 452. In an embodiment NELOS data 432 can be the same as TFLinformation 452. In other embodiments, NELOS data 432 can be differentfrom TFL information 452. As such, NELOS data 432 can comprise near realtime location or location data, historical location or location data,cached location or location data, etc. These types of location relatedinformation, e.g., TFL information 452, etc., can be distinct from moreconventional types of location related information, such as that fromGPS, triangulation, trilateration, beacon ranging, etc. As such, the useof TFL information 452, NELOS information 432, etc., in combination withthe instant disclosure can provide, as disclosed herein, advantages overconventional technologies.

In an aspect, NELOS data 432, once received by LDSC 410, can be storedat NELOS data store 414. NELOS data store 414 can further be employed tostore and update SDD 442. In an embodiment, LDSC 410 can receive moreNELOS data 432 than can be associated with subscription request 422,whereby LDSC 410 can store a portion of NELOS data 432 at NELOS datastore 414. In another embodiment, NELOS data store 414 can retain excessNELOS data 432 to allow for potential updates to subscription request422.

LDSC 410 can analyze NELOS data 432 and/or data stored on NELOS datastore 414 via NELOS data analysis component 416 to facilitatedetermining SDD 442. Nearly any analysis can be performed at NELOS dataanalysis component 416. As an example, data can be aggregated,personally identifying information can be removed, average values can begenerated, trends can be determined, locations, modes of travel, etc.

LDSC 410 can further comprise subscription rule component 418. In anembodiment, subscription rule component 418 can store a rule related tosubscription request 422. In another embodiment, subscription rulecomponent 418 can update a rule based on subscription request 422. In afurther embodiment, subscription rule component 418 can apply a rulerelated to a subscription request, e.g., subscription request 422.Application of a rule by subscription rule component 418 can affectinformation stored at NELOS data store 414, can affect analysisperformed by NELOS data analysis component 416, can adjust TFLinformation retention, e.g., via updating TFL information retention rule412, etc. In an embodiment, subscription rule component 418 can apply atiered or ordered rule. As an example, subscription request 422 caninclude a rule update for subscription rule component 418 such thatwhere the subscriber has a plurality of stored subscription requests forboth smartphones and tablet computers, subscription request 422 canresult in an update to only the tablet computer requests and thesmartphone requests can remain unaltered.

In some embodiments, UE 450 can further comprise TFL information store454. TFL information store 454 can store TFL information related to UE450. In an aspect, this can be related to determining TFL information452. In an embodiment, TFL information 452 can comprise information fromTFL information store 454. Further, TFL information store 454 can storeTFL information based on received TFL information retention rule 434.TFL information retention rule 434 can be based on TFL informationretention rule 412. In an embodiment, NELOS component 432 can pass TFLinformation retention rule 412 through as TFL information retention rule432, e.g., TFL information retention rule 412 can remain unchanged. Inanother embodiment, TFL information retention rule 412 can be receivedby NELOS component 430, which in turn can generate TFL informationretention rule 432 based on TFL information retention rule 412. As such,TFL information retention rule 432 can be the same as, partially thesame as, or related to yet different from TFL information retention rule412.

FIG. 5 illustrates a system 500 that facilitates access to mobile devicelocation information via a cloud-based deployment in accordance withaspects of the subject disclosure. Scheme 500 illustrates location datasubscription component (LDSC) 510 that can receive subscription request522 via virtual machine (VM) 590. VM 590 can be executing in an internetbased cloud environment (hereinafter, ‘the cloud’). The cloud can enabledeployment of VM 590 comprising LDSC 510 on devices that may not bephysically considered as carrier-side devices. However, in someembodiments where a carrier is closely related to the operation of VM590, LDSC 510 can logically be considered as a carrier-side component.In other embodiments, VM 590 can be associated with another party thatcan have an agreement to receive NELOS data 532, e.g., a mobile networkoperator (MNO) or mobile virtual network operator (MVNO) can operate alocation service via VM 590 and license NELOS data 532 to allow them toprovide location services to a third party, e.g., via SDD 542.

LDSC 510 can further receive subscription request 522 via VM 590 in thecloud. Subscription request 522 can comprise a parameter related tosubscriber data deliverable (SDD) 542, such as frequency of reporting, areporting trigger such as an event, proximity, time, identifier(s),etc., a type of returned data such as location, timing information,derivatives of location or timing information, etc., price, device, age,etc.

LDSC 510 can further receive NELOS data 532 via VM 590. NELOS data 532can comprise location data related to a mobile device or other UE. LDSC510 can facilitate access to SDD 542, via VM 590, based on NELOS data532 and subscription request 522. SDD 542 can comprise a location,location data, TFL information, NELOS information, derivatives thereof,or other related information.

In an embodiment, NELOS data 532 can be sourced from a NELOS component,e.g., NELOS component 230 in FIG. 2, etc., from a UE directly, or viaanother component such as a data store, another cloud-based virtualdevice, etc. NELOS data 532 can comprise TFL or TFL information. Assuch, NELOS data 532 can comprise near real time location or locationdata, historical location or location data, cached location or locationdata, etc. NELOS data 532 can be distinct from more conventional typesof location related information, such as that from GPS, triangulation,trilateration, beacon ranging, etc. As such, the use of TFL, TFLinformation, NELOS information, NELOS technology, etc., in combinationwith the instant disclosure provides advantages over conventionaltechnologies.

In an aspect, NELOS data 532 can be analyzed at LDSC 510 in generatingSDD 542. In an embodiment, NELOS data 532 can be passed as SDD 542without change, e.g., the analysis does not change NELOS data 532. Inother embodiments, NELOS data 532 can be processed, analyzed, etc., suchthat SDD 542 comprises information derived from NELOS data 532, e.g.,SDD 542 is not the same as NELOS data 532. As an example, where LDSC 510analyzes NELOS data 532 and determines that a portion of it isassociated with a minor child, this portion can be blocked and thebalance of the information can be made available as SDD 542.

In an embodiment, LDSC 510 can make control information, rules, etc.,available to a NELOS component, such as NELOS component 230 in FIG. 2,etc., or to a UE, such as UE 250 of FIG. 2, etc., via an internet linkbetween VM 590 and the NELOS component or UE. As an example, a rule canbe communicated to a UE from LDSC 510 via VM 590 that can allow the UEto selectively store location information, TFL information, etc., andreturn the stored information to LDSC 510, via NELOS data 532, in accordwith the rule. This aspect can enable a variety of componentconfigurations comprising, for example, UEs sourcing locationinformation or timing information, NELOS components determining TFLinformation, LDSC 510 receiving NELOS data 532, and making SDD 542available to other components or devices not illustrated in system 500.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIG. 6-FIG. 8. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, two or more of the disclosed example methods can be implemented incombination with each other, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methodsdisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 6 illustrates a method 600 facilitating access to mobile devicelocation information in accordance with aspects of the subjectdisclosure. At 610, method 600 can include receiving a subscriptionrequest. A subscription request can comprise a parameter related tolocation information to be made available, e.g., SDD 142, etc. Theparameter can include aspects such as frequency of reporting, areporting trigger, such as an event, proximity to a locus, a time, anelapsed time, an identifier(s), etc., a type of data to return, such aslocation type, timing type information, derivative type, etc., a price,a device or model, an age, etc. In an aspect, a subscription request canbe received from a third party and can facilitate returning locationinformation back to the third party. In some embodiments, thesubscription request can be a one-time data request, a multi-part datarequest, an on-going data request, etc.

At 620, method 600 can comprise receiving NELOS data, e.g., NELOS data132, etc., related to the subscription request at 610. NELOS data cancomprise location data related to a mobile device or other UE. NELOSdata can be received, for example, from a NELOS component such as NELOScomponent 230 in FIG. 2, etc., from a UE directly, or via anothercomponent such as a data store, cloud environment device, etc. NELOSdata can comprise TFL or TFL information. As such, NELOS data cancomprise near real time location or location data, historical locationor location data, cached location or location data, etc. The particularsof capturing, determining, or generating TFL, TFL information, or NELOSinformation is outside of the scope of the instant disclosure exceptwhere more particularly pointed out herein and to note that these typesof location related information, e.g., TFL information, etc., aredistinct from more conventional types of location related information,such as that from GPS, triangulation, trilateration, beacon ranging,etc. As such, the use of TFL, TFL information, NELOS information, NELOStechnology, etc., in combination with the instant disclosure providesadvantages over conventional technologies.

At 630, method 600 can include facilitating access to locationinformation to be made available, e.g., SDD 142, etc., based on theNELOS data at 620 and the subscription request at 610. At this point,method 600 can end. The location information can comprise a location,location data, TFL information, NELOS information, derivatives thereof,or other related information. In an embodiment, NELOS data can be madeavailable, in response to receiving the subscription request at 610,without change. In other embodiments, NELOS data can be processed,analyzed, etc., such that the information made available, in response tothe subscription request at 610, comprises information derived fromNELOS data, e.g., the information made available can be different fromthe NELOS data.

FIG. 7 illustrates a method 700 that facilitates pushing mobile devicelocation information to a subscriber and employing control informationin accordance with aspects of the subject disclosure. At 710, method 700can include can include receiving a subscription request from a thirdparty device. A subscription request can comprise a parameter related tolocation information to be made available. A third party device can be adevice associated with an entity identifier other than one associatedwith a carrier identity or a mobile device user identity. In someembodiments, the subscription request can be a one-time data request, amulti-part data request, an on-going data request, etc. In someembodiments, the subscription request can further comprise a rule. Therule can be related to filtering NELOS data or selecting a subset ofNELOS data that comports with the intent of the subscription request. Asan example, the rule can relate not only to how often the location datacan be accessed, but also as to the type of NELOS data, range of NELOSdata, etc., that can be made available to a third party device undermethod 700.

At 720, method 700 can comprise determining control information. In anembodiment, control information can communicated to a UE that can allowthe UE to selectively store location information, TFL information, etc.,and return the stored information, e.g., as NELOS data or a precursorthereto, in accord with the rule. The control information can be relatedto retention of a set of TFL information at the UE and can be based onan aspect of the subscription request at 710. This aspect can enable avariety of component configurations comprising, for example, UEssourcing location information or timing information, NELOS componentsdetermining TFL information, etc. Some of these component configurationsare illustrated in the instant figures, though not all configurationsare illustrated for clarity and brevity.

At 730, method 700 can comprise receiving NELOS data related to thesubscription request at 710. NELOS data can comprise location datarelated to a mobile device or other UE. NELOS data can be received, forexample, from a NELOS component, from a UE directly, or via anothercomponent such as a data store, cloud environment device, etc. NELOSdata can comprise TFL or TFL information. As such, NELOS data cancomprise near real time location or location data, historical locationor location data, cached location or location data, etc.

At 740, method 700 can include facilitating access to a subscriber datadeliverable (SDD), e.g., SDD 142, etc., based on the NELOS data at 730,subject to the control information at 720, and the subscription requestat 710. At this point, method 700 can end. The SDD can then be madeavailable to the third party device via a ‘push’ of the data. Thelocation information can comprise a location, location data, TFLinformation, NELOS information, derivatives thereof, or other relatedinformation. In an embodiment, NELOS data can be made available, inresponse to receiving the subscription request at 710, without change.In other embodiments, NELOS data can be processed, analyzed, etc., suchthat the SDD, in response to the subscription request at 710, comprisesinformation derived from NELOS data, e.g., the information madeavailable can be different from the NELOS data.

FIG. 8 illustrates a method 800 that facilitates access to mobile devicelocation information and analysis in accordance with aspects of thesubject disclosure. At 810, method 800 can include can include receivinga subscription request from a third party device. A subscription requestcan comprise a parameter related to location information to be madeavailable. In an embodiment, a third party device can be a deviceassociated with an entity identifier other than one associated with acarrier identity or a mobile device user identity. In anotherembodiment, a third party device can be another device on thecarrier-side or user-side. As an example, a third party device can beanother device of the carrier that can be treated as an ‘independententity’ divorced from the NELOS/TFL components, such as, providinglocation information to an application executing on another carrierserver, an application executing on another UE, an MVNO virtual deviceexecuting in a VM on a carrier device, etc.

At 820, method 800 can update a set of rules based on an aspect of thesubscription request. In some embodiments, the subscription request caninclude a parameter reflecting an number of SDD accesses permitted,e.g., a one-time SDD access, multiple updated SDD access, on-goingupdated SDD access, etc. In other embodiments, the subscription requestcan also comprise a rule related to filtering NELOS data or selecting asubset of NELOS data that comports with the intent of the subscriptionrequest.

At 830, method 800 can comprise determining control information. In anembodiment, control information can communicated to a UE that can allowthe UE to selectively store location information, TFL information, etc.,and return the stored information, e.g., as NELOS data or a precursorthereto, in accord with the control information. The control informationcan be related to retention of a set of TFL information at the UE andcan be based on an aspect of the subscription request at 810. Thisaspect can enable a variety of component configurations comprising, forexample, UEs sourcing location information or timing information, NELOScomponents determining TFL information, etc. Some of these componentconfigurations are illustrated in the instant figures, though not allconfigurations are illustrated for clarity and brevity.

At 840, method 800 can comprise receiving NELOS data related to thesubscription request at 810. NELOS data can comprise location datarelated to a mobile device or other UE. NELOS data can be received, forexample, from a NELOS component, from a UE directly, or via anothercomponent such as a data store, cloud environment device, etc. NELOSdata can comprise TFL or TFL information. As such, NELOS data cancomprise near real time location or location data, historical locationor location data, cached location or location data, etc.

At 850, method 800 can comprise generating an SDD based on an analysisof the NELOS data at 840 and the subscription request at 810, subject tothe control information at 830 and the rules at 820. The SDD cancomprise a location, location data, TFL information, NELOS information,derivatives thereof, or other related information.

At 860, method 800 can include facilitating access to the SDD. At thispoint, method 800 can end. In an embodiment, the SDD can then be madeavailable to the third party device via a ‘push’ of the data. In anotherembodiment, the SDD can then be made available to the third party devicevia a ‘pull of the data by the third party device. In a furtherembodiment, the SDD can then be made available to the third party devicevia a publishing of the data such that the third party device can pollthe data independently. In an embodiment, NELOS data can be processed,analyzed, etc., such that the SDD, in response to the subscriptionrequest at 810, comprises information derived from NELOS data, e.g., theinformation made available can be different from the NELOS data. Ofnote, the analysis may result in no change of the NELOS data provided asthe SDD, e.g., the g., the information made available can be the same asthe NELOS data.

FIG. 9 is a schematic block diagram of a computing environment 900 withwhich the disclosed subject matter can interact. The system 900 includesone or more remote component(s) 910. The remote component(s) 910 can behardware and/or software (e.g., threads, processes, computing devices).In some embodiments, remote component(s) 910 can include servers,personal servers, wireless telecommunication network devices, etc. As anexample, remote component(s) 910 can be a UE 250, 350, 450, etc., thirdparty component 220, etc., NELOS component 230, 330, 430, etc.

The system 900 also includes one or more local component(s) 920. Thelocal component(s) 920 can be hardware and/or software (e.g., threads,processes, computing devices). In some embodiments, local component(s)920 can include, for example, LDSC 110, 210, 310, 410, 510, etc., NELOScomponent 230, 330, 430, etc., VM 590, etc.

One possible communication between a remote component(s) 910 and a localcomponent(s) 920 can be in the form of a data packet adapted to betransmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 910 and a local component(s)920 can be in the form of circuit-switched data adapted to betransmitted between two or more computer processes in radio time slots.The system 900 includes a communication framework 940 that can beemployed to facilitate communications between the remote component(s)910 and the local component(s) 920, and can include an air interface,e.g., Uu interface of a UMTS network. Remote component(s) 910 can beoperably connected to one or more remote data store(s) 950, such as ahard drive, SIM card, device memory, etc., that can be employed to storeinformation on the remote component(s) 910 side of communicationframework 940. Similarly, local component(s) 920 can be operablyconnected to one or more local data store(s) 930, that can be employedto store information on the local component(s) 920 side of communicationframework 940.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that performs particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can include both volatile and nonvolatile memory,by way of illustration, and not limitation, volatile memory 1020 (seebelow), non-volatile memory 1022 (see below), disk storage 1024 (seebelow), and memory storage 1046 (see below). Further, nonvolatile memorycan be included in read only memory, programmable read only memory,electrically programmable read only memory, electrically erasable readonly memory, or flash memory. Volatile memory can include random accessmemory, which acts as external cache memory. By way of illustration andnot limitation, random access memory is available in many forms such assynchronous random access memory, dynamic random access memory,synchronous dynamic random access memory, double data rate synchronousdynamic random access memory, enhanced synchronous dynamic random accessmemory, Synchlink dynamic random access memory, and direct Rambus randomaccess memory. Additionally, the disclosed memory components of systemsor methods herein are intended to comprise, without being limited tocomprising, these and any other suitable types of memory.

Moreover, it is noted that the disclosed subject matter can be practicedwith other computer system configurations, including single-processor ormultiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., personal digital assistant, phone, watch, tablet computers,netbook computers, . . . ), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network; however, some if not all aspects ofthe subject disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules can be located inboth local and remote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, part of LDSC 110,210, 310, 410, 510, etc., NELOS component 230, 330, 430, etc., VM 590,etc., UE 250, 350, 450, etc., third party component 220, etc., includesa processing unit 1014, a system memory 1016, and a system bus 1018.System bus 1018 couples system components including, but not limited to,system memory 1016 to processing unit 1014. Processing unit 1014 can beany of various available processors. Dual microprocessors and othermultiprocessor architectures also can be employed as processing unit1014.

System bus 1018 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire (Institute of Electricaland Electronics Engineers 1194), and small computer systems interface.

System memory 1016 can include volatile memory 1020 and nonvolatilememory 1022. A basic input/output system, containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can includeread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable read only memory,or flash memory. Volatile memory 1020 includes read only memory, whichacts as external cache memory. By way of illustration and notlimitation, read only memory is available in many forms such assynchronous random access memory, dynamic read only memory, synchronousdynamic read only memory, double data rate synchronous dynamic read onlymemory, enhanced synchronous dynamic read only memory, Synchlink dynamicread only memory, Rambus direct read only memory, direct Rambus dynamicread only memory, and Rambus dynamic read only memory.

Computer 1012 can also include removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk read only memory device, compact disk recordabledrive, compact disk rewritable drive or a digital versatile disk readonly memory. To facilitate connection of the disk storage devices 1024to system bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, read only memory, programmable read only memory,electrically programmable read only memory, electrically erasable readonly memory, flash memory or other memory technology, compact disk readonly memory, digital versatile disk or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or other tangible media which can be used tostore desired information. In this regard, the term “tangible” herein asmay be applied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating intangible signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can includenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium. As such, for example, a computer-readable medium can compriseexecutable instructions stored thereon that, in response to execution,cause a system comprising a processor to perform operations, comprising:receiving a subscription request from a third party component, whereinthe request is related to facilitating access to location data by thesystem, e.g., LDSC 110, 210, 310, 410, 510, etc., and in response to thereceiving the subscription request, receiving NELOS data by the system,and pushing the location data to the third party component, without anadditional request by the third party component.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software includes an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. As an example, a user interface can allow entry ofaspects of a subscription request via third party component 220, etc.,and can be embodied in a touch sensitive display panel, a mouse inputGUI, a command line controlled interface, etc., allowing a user tointeract with computer 1012. Input devices 1036 include, but are notlimited to, a pointing device such as a mouse, trackball, stylus, touchpad, keyboard, microphone, joystick, game pad, satellite dish, scanner,TV tuner card, digital camera, digital video camera, web camera, cellphone, smartphone, tablet computer, etc. These and other input devicesconnect to processing unit 1014 through system bus 1018 by way ofinterface port(s) 1038. Interface port(s) 1038 include, for example, aserial port, a parallel port, a game port, a universal serial bus, aninfrared port, a Bluetooth port, an IP port, or a logical portassociated with a wireless service, etc. Output device(s) 1040 use someof the same type of ports as input device(s) 1036.

Thus, for example, a universal serial busport can be used to provideinput to computer 1012 and to output information from computer 1012 toan output device 1040. Output adapter 1042 is provided to illustratethat there are some output devices 1040 like monitors, speakers, andprinters, among other output devices 1040, which use special adapters.Output adapters 1042 include, by way of illustration and not limitation,video and sound cards that provide means of connection between outputdevice 1040 and system bus 1018. It should be noted that other devicesand/or systems of devices provide both input and output capabilitiessuch as remote computer(s) 1044. As an example, vehicle subsystems, suchas headlights, brake lights, stereos, vehicle information sharingdevice, etc., can include an output adapter 1042 to enable use inaccordance with the presently disclosed subject matter.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, cloud service, a workstation, amicroprocessor based appliance, a peer device, or other common networknode and the like, and typically includes many or all of the elementsdescribed relative to computer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies include fiber distributed data interface, copperdistributed data interface, Ethernet, Token Ring and the like. Wide areanetwork technologies include, but are not limited to, point-to-pointlinks, circuit-switching networks like integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines. As noted below, wireless technologies may be used inaddition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and digital subscriber line modems,integrated services digital network adapters, and Ethernet cards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures such as, but not limited to,molecular and quantum-dot based transistors, switches and gates, inorder to optimize space usage or enhance performance of user equipment.A processor may also be implemented as a combination of computingprocessing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Further, the term “include” is intended to be employed as an open orinclusive term, rather than a closed or exclusive term. The term“include” can be substituted with the term “comprising” and is to betreated with similar scope, unless otherwise explicitly used otherwise.As an example, “a basket of fruit including an apple” is to be treatedwith the same breadth of scope as, “a basket of fruit comprising anapple.”

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, can refer to a wirelessdevice utilized by a wireless services subscriber or user of a wirelesscommunication service to receive or convey data, control, voice, video,sound, gaming, or substantially any data-stream or signaling-stream. Theforegoing terms are utilized interchangeably in the subjectspecification and related drawings. Likewise, the terms “access point,”“base station,” “Node B,” “evolved Node B,” “home Node B,” “home accesspoint,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream to and from a set ofsubscriber stations or provider enabled devices. Data and signalingstreams can include packetized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio access network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include broadcasttechnologies (e.g., sub-Hertz, extremely low frequency, very lowfrequency, low frequency, medium frequency, high frequency, very highfrequency, ultra-high frequency, super-high frequency, terahertzbroadcasts, etc.); Ethernet; X.25; powerline-type networking, e.g.,Powerline audio video Ethernet, etc.; femtocell technology; Wi-Fi;worldwide interoperability for microwave access; enhanced general packetradio service; third generation partnership project, long termevolution; third generation partnership project universal mobiletelecommunications system; third generation partnership project 2, ultramobile broadband; high speed packet access; high speed downlink packetaccess; high speed uplink packet access; enhanced data rates for globalsystem for mobile communication evolution radio access network;universal mobile telecommunications system terrestrial radio accessnetwork; or long term evolution advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A system comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receiving arequest for mobile device location information from a subscribing deviceassociated with a subscriber identity; and in response to receivingnetwork event locating system (NELOS) information related to a locationof a mobile device, facilitating access to location data related to theNELOS information based on a parameter of the request satisfying a rulerelated to a permission to access the location data, wherein the NELOSinformation comprises an estimation of a geographic location of themobile device based on a differential time measurement between themobile device and a first and second NodeB device, a first historicgeographic location value for a first NodeB site pair of devicescomprising the first NodeB device, and a second historic geographiclocation value for a second NodeB site pair of devices comprising thesecond NodeB device.
 2. The system of claim 1, wherein the facilitatingthe access to the location data comprises pushing the location data tothe subscribing device without requiring a further request from thesubscribing device.
 3. The system of claim 1, wherein the facilitatingthe access to the location data comprises publishing the location datato facilitate a polling of the location data by the subscribing devicewithout receiving a further request from the subscribing device.
 4. Thesystem of claim 1, wherein the facilitating the access to the locationdata comprises receiving a subsequent request from the subscribingdevice to access the location data.
 5. The system of claim 1, whereinthe parameter of the request comprises an indicator of a one-time accessto the location data by the subscribing device.
 6. The system of claim5, wherein the parameter of the request comprises an indicator of acontinuing access to the location data by the subscribing device, andwherein the continuing access is allowed until a condition related tothe continuing access is satisfied.
 7. The system of claim 1, whereinthe NELOS information is related to idle-state timed fingerprintlocation information.
 8. The system of claim 1, wherein the execution ofthe executable instructions occurs in a network device of an internetbased cloud environment.
 9. A method, comprising: receiving, by a devicecomprising a processor, a subscription request from a subscribingdevice; receiving, by the device, network event locating system (NELOS)information related to a location of a user equipment, wherein the NELOSinformation comprises an estimation of a geographic location of the userequipment based on a differential time measurement related to adisposition of the user equipment relative to a first NodeB device and asecond NodeB device, a first historic geographic location value for afirst NodeB site pair of devices comprising the first NodeB device, anda second historic geographic location value for a second NodeB site pairof devices comprising the second NodeB device; and enabling, by thedevice, access to a data deliverable, by the subscribing device, whereinthe data deliverable comprises information related to the NELOSinformation based on the subscription request.
 10. The method of claim9, wherein the enabling the access to the data deliverable comprisesaccessing the data deliverable via a push of information to thesubscribing device without an additional request from the subscribingdevice.
 11. The method of claim 9, wherein the enabling the access tothe data deliverable comprises publishing the data deliverable tofacilitate a polling of the data deliverable by the subscribing devicewithout an additional request from the subscribing device.
 12. Themethod of claim 9, wherein a parameter of the subscription requestcomprises an indicator of a number of accesses to the data deliverableenabled by the device for the subscribing device.
 13. The method ofclaim 12, wherein the number of accesses is one access.
 14. The methodof claim 12, wherein the number of accesses is more than one access. 15.The method of claim 9, wherein the NELOS information is related toidle-state timed fingerprint location information.
 16. Amachine-readable storage medium, comprising executable instructionsthat, when executed by a processor, facilitate performance ofoperations, comprising: receiving a request for mobile device locationinformation from a subscribing device associated with a subscriberidentity; receiving network event locating system (NELOS) informationrelated to a location of a mobile device, wherein the NELOS informationcomprises an estimation of a geographic location of the mobile devicebased on a differential time measurement related to a proximity of themobile device to a first NodeB device and a second NodeB device, a firsthistoric geographic location value for a first NodeB site pair ofdevices comprising the first NodeB device, and a second historicgeographic location value for a second NodeB site pair of devicescomprising the second NodeB device; generating location data in responseto an analysis of the NELOS information based on the request; andsharing the location data with the subscribing device.
 17. Themachine-readable storage medium of claim 16, wherein the sharing thelocation data comprises pushing the location data to the subscribingdevice without requiring a further request from the subscribing device.18. The machine-readable storage medium of claim 16, wherein a parameterof the request comprises an indicator of a number of shares of thelocation data with the subscribing device.
 19. The machine-readablestorage medium of claim 18, wherein the number of shares is more thanone share.
 20. The computer machine-readable storage medium of claim 16,wherein the NELOS information is related to idle-state timed fingerprintlocation information.